Find first the exact SDK request and add the forcing of 32 bit build to VS 2005 #276
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently when I specify to use version 6.0A it search in the loop on-
C:/Program Files (x86)/Windows Kits
C:/Program Files (x86)/Microsoft SDKs/Windows
C:/Program Files/Windows Kits
C:/Program Files/Microsoft SDKs/Windows
Now, since it ignores only higher versions of SDK (Not Lower), It detect version 5.0 under
C:\Program Files (x86)\Microsoft SDKs\Windows
Before it detects-
C:\Program Files\Microsoft SDKs\Windows\v6.0A
This means it use version 5.0 when I asked for 6.0A.
The solution is to do two loops instead of one-
I am not sure why we need lower version of SDK, but this is how it was implemented first, so I did not want to cancel this option.